docs(README): add @modelcontextprotocol/fastify to middleware listing#2113
docs(README): add @modelcontextprotocol/fastify to middleware listing#2113sceran wants to merge 1 commit into
@modelcontextprotocol/fastify to middleware listing#2113Conversation
The fastify middleware package (private: false, 2.0.0-alpha.2) is published alongside node, express, and hono, but was absent from the top-level README in three places: overview, middleware section, and install commands. Closes modelcontextprotocol#2112
|
@modelcontextprotocol/client
@modelcontextprotocol/server
@modelcontextprotocol/express
@modelcontextprotocol/fastify
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
|
Rechecked |
3 participants
What
Add
@modelcontextprotocol/fastifyto the README in the three places where the other middleware packages are documented.Why
The fastify middleware package is published (
packages/middleware/fastify/package.jsonhasprivate: falseand shares the same2.0.0-alpha.2version as node/express/hono) and has its own README, but the top-level README omits it everywhere — overview line, middleware section, and install commands. Looks like an oversight from when fastify was added rather than an intentional exclusion. See #2112 for the original observation.How
Three small additions, no removals:
(Express, Hono, Node.js HTTP)→(Express, Hono, Fastify, Node.js HTTP)@modelcontextprotocol/fastifybullet after the hono entry, using the same description shape Express uses.npm install @modelcontextprotocol/fastify fastifysnippet matching the hono entry.Behavior change
node,express,hono. Fastify is invisible to anyone reading the top-level docs.Breaking changes
None — docs only.
Test plan
No code paths touched. Spot-checked rendered Markdown locally.
Related
@modelcontextprotocol/fastifymissing from middleware listing #2112Code drafted with Claude Code assistance; manually reviewed and tested.